You are here:

CI Project

CI Project iCube enables you to create ad hoc reports that help you to track the build performance of the applications handled by individual teams in comparison with the desired build frequencies. You can generate different types of health reports such as stability report, quality report, and so on. CI Project iCube also enables you generate health reports every day to understand the health report trend of your builds.

Attributes

Expand this link to view the list of attributes available as part of the CI Project iCube:

Attributes	Description
Build Project	Project to which the build is associated with
Build Project Description	A brief description about the build
Build Project URL	URL of the build
First Build Run Name	Name of the first build that run for the project
First Build Run Number	Number of the first build that run for the project
Last Build Name	Name of the last build
Last Build Number	Unique identification number of the last build
Last Completed Build Name	Name of the last completed build
Last Completed Build Number	Unique identification number of the last completed build
Last Failed Build Name	Name of the last build that failed
Last Failed Build Number	Unique identification number of the last build that failed
Last Stable Build Name	Name of the last stable build
Last Stable Build Number	Unique identification number of the last stable build
Last Successful Build Name	Name of the last successful build
Last Successful Build Number	Unique identification number of the last successful build
Last Unstable Build Name	Name of the last unstable build
Last Unstable Build Number	Unique identification number of the last unstable build
Last Unsuccessful Build Name	Name of the last unsuccessful build
Last Unsuccessful Build Number	Unique identification number of the last unsuccessful build

Metrics

Expand this link to view the list of metrics available as part of the CI Project iCube:

Metric	Description	Formula/Condition	Expected Value
Build Stability Score	Stability score across all builds for a project	(([Builds Passed] / [Builds Total]))	Higher the number, better is the score
Builds Aborted	Number of builds that were aborted	Sum([Builds Aborted])	Closer to 0 is ideal
Builds Failed	Number of builds that failed to execute	Sum([Builds Failed])	Closer to 0 is ideal
Builds Not Executed	Number of builds that could not be executed	Sum([Builds Not Executed])	Closer to 0 is ideal
Builds Passed	Number of builds that passed successfully	Sum([Builds Passed])	Higher number is ideal
Builds Total	Total number of builds	Sum([Builds Total])	>0
Builds Unstable	Number of unstable builds	Sum([Builds Unstable])	Closer to 0 is ideal
Cobertura Score	Cobertura score indicates the percentage of code accessed by tests. It can be used to identify parts of your program that lack test coverage	Sum([Cobertura Score])	Higher is ideal
Test Automation Score	Test score for the latest build. Calculated as test passed divided by the total number of tests	(([Tests Passed] / [Tests Total]))	Higher is ideal
Tests Failed	The number of test cases that failed for a job build. The value reported is a roll-up or aggregate of all child builds. Supported only for Jenkins source.	Sum([Tests Failed])	Closer to 0 is ideal
Tests Passed	The number of test cases that were successful for a job build. The value reported is a roll-up/aggregate of all child builds. Supported only for Jenkins source.	Sum([Tests Passed])	>0
Tests Skipped	The number of test cases skipped (not run) for a job build. The value reported is a roll-up/aggregate of all child builds. Supported only for Jenkins source.	Sum([automated test skip count])	Closer to 0 is ideal
Tests Total	The total number of test cases for a job build (sum of Tests Passed, Failed and Skipped). The value reported is a roll-up/aggregate of all child builds. Supported only for Jenkins source.	([Tests Passed] + [Tests Failed]) + [Tests Skipped]	>0